NTISthis.com

Evidence Guide: ICTSAD604 - Manage and communicate ICT solutions

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTSAD604 - Manage and communicate ICT solutions

What evidence can you provide to prove your understanding of each of the following citeria?

Manage identified client ICT requirements and scope of solution

  1. Establish baseline client ICT requirements and change control processes to track changes to requirements and solution scope
  2. Resolve issues and conflicts that emerge during final stages of identifying and analysing requirements
  3. Determine how requirements will be presented for review
  4. Secure approval of requirements from those stakeholders who have the appropriate authority
Establish baseline client ICT requirements and change control processes to track changes to requirements and solution scope

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Resolve issues and conflicts that emerge during final stages of identifying and analysing requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine how requirements will be presented for review

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Secure approval of requirements from those stakeholders who have the appropriate authority

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage requirement relationships and dependencies

  1. Examine and organise the set of requirements and record the dependencies and relationships for each
  2. Perform impact analysis to assess or evaluate the impact of a change
  3. Deploy requirements management tools as necessary
Examine and organise the set of requirements and record the dependencies and relationships for each

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Perform impact analysis to assess or evaluate the impact of a change

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Deploy requirements management tools as necessary

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Maintain requirements for re-use

  1. Identify requirements that the organisation will use in the long term
  2. Name and define requirements available for future re-use
Identify requirements that the organisation will use in the long term

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Name and define requirements available for future re-use

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare requirements package

  1. Decide which formats are appropriate for a particular project and its stakeholders
  2. Prepare requirements package according to organisational need
Decide which formats are appropriate for a particular project and its stakeholders

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare requirements package according to organisational need

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Manage identified client ICT requirements and scope of solution

1.1 Establish baseline client ICT requirements and change control processes to track changes to requirements and solution scope

1.2 Resolve issues and conflicts that emerge during final stages of identifying and analysing requirements

1.3 Determine how requirements will be presented for review

1.4 Secure approval of requirements from those stakeholders who have the appropriate authority

2. Manage requirement relationships and dependencies

2.1 Examine and organise the set of requirements and record the dependencies and relationships for each

2.2 Perform impact analysis to assess or evaluate the impact of a change

2.3 Deploy requirements management tools as necessary

3. Maintain requirements for re-use

3.1 Identify requirements that the organisation will use in the long term

3.2 Name and define requirements available for future re-use

4. Prepare requirements package

4.1 Decide which formats are appropriate for a particular project and its stakeholders

4.2 Prepare requirements package according to organisational need

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Manage identified client ICT requirements and scope of solution

1.1 Establish baseline client ICT requirements and change control processes to track changes to requirements and solution scope

1.2 Resolve issues and conflicts that emerge during final stages of identifying and analysing requirements

1.3 Determine how requirements will be presented for review

1.4 Secure approval of requirements from those stakeholders who have the appropriate authority

2. Manage requirement relationships and dependencies

2.1 Examine and organise the set of requirements and record the dependencies and relationships for each

2.2 Perform impact analysis to assess or evaluate the impact of a change

2.3 Deploy requirements management tools as necessary

3. Maintain requirements for re-use

3.1 Identify requirements that the organisation will use in the long term

3.2 Name and define requirements available for future re-use

4. Prepare requirements package

4.1 Decide which formats are appropriate for a particular project and its stakeholders

4.2 Prepare requirements package according to organisational need

Evidence of the ability to:

establish processes to:

trace requirements

control and track changes to requirements

scope solutions

manage requirement relationships

package and communicate requirements according to what is appropriate for a project or stakeholder group.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain conflict resolution and issue management techniques to handle possible changes to solution scope

outline requirements management and traceability processes

list and apply techniques for managing version control and configuration.